| Fixed |
Explanation |
Actions required |
Severity |
| Device was withdrawn |
Device was withdrawn from BizMobile Go! device management. There is no problem if device was intentionally withdrawn by Device Management Operator. |
Operator can delete this device by clicking trash icon. But if this was not intended by the Operator and device user intentionally deleted the remote management profile, Operator must confirm the reason why device user deleted it. |
Warning |
| Device was reenrolled with another identifier |
Same device was checked-in with another identifier (device registration was duplicated). Only one device identifier is allowed to manage device. |
Old device identifier is withdrawn soon after device is re-enrolled. But Operator should confirm with device user about the reasons why device was re-enrolled. |
Warning |
| Device was not responding |
This alarm is raised when device was not responding for 3 days(default setting). It could be the following reasons why device was not responding. Device is turned off Device is not connected to the network Device was withdrawn by wipe, or recovered from the backup (Apple Push Certificate was removed). |
There is no problem if device is turned off. As long as device is enrolled, connection will be resumed when device is connected to the network. There is a possibility that device was withdrawn. To confirm device enrollment status, connect device to the network. Please delete this device if there is no need to manage it anymore. |
Major |
| Device push notification token has expired |
This occurs when the server sends a push notification to the device, but the active token has expired. |
Clicking on the edit icon on the right side will take you to the device editing screen, where you can extend the check-in expiration date. Additionally, it may require actions such as sending reminders to the device user. |
Warning |
| Device registration has expired |
Device was not checked-in before the expiration date and enrollment period has expired. |
By clicking Edit icon, Operator can extend expiration date for 7 days. But Operator should remind device user to check-in the device. |
Minor |
| Device registration restriction was violated |
This alarm is raised when device was checked in with incorrect enrollment restrictions. That device will be withdrawn automatically. |
If this is due to typo of the enrollment restriction, please recreate the device info with correct enrollment restriction(s). Else, Operator needs to confirm correct device is tried to check-in. |
Warning |
| Device was jailbroken |
Device was Jailbroken. |
Need to ask device user not to Jailbreak the device. |
Warning |
| Device was rooted |
Device was rooted. |
Need to ask device user not to root the device. |
Warning |
| Device message was unread |
This alarm is raised when message sent to the device was not read within the set time frame. |
This alarm is just FYI for device management. Operator can delete this alarm by clicking trash icon once confirmed. |
Warning |
| Device administration has been turned off |
Device administration has been turned off. |
Need to ask device user to enable device administration for MDM agent application. |
Warning |
| Device owner issued a device lock command |
(BizMobile Go! Personal usage only) Device owner issued a Lock command. |
This alarm is just FYI for Device Management Operator. Operator can delete this alarm by clicking trash icon once confirmed. |
Warning |
| Device owner issued a soft wipe command |
(BizMobile Go! Personal usage only) Device owner issued a Wipe command. |
This alarm is just FYI for Device Management Operator. Operator can delete this alarm by clicking trash icon once confirmed. |
Warning |
| Device owner issued a device erase command |
(BizMobile Go! Personal usage only) Device owner issued a Selective Wipe command. |
This alarm is just FYI for Device Management Operator. Operator can delete this alarm by clicking trash icon once confirmed. |
Warning |
| Device has no passcode |
(iOS device only) This alarm is raised when iOS device has no passcode. |
Need to ask or remind device user to set passcode (if passcode policy is enabled by Configuration Profile, password set prompt is shown on the device) |
Warning |
| Device does not have compliant passcode |
This alarm is raised when passcode set on the device is not compliant with passcode policy which configured by the profile. |
Need to ask or remind device user to set compliant passcode (Password set prompt is shown on the device). |
Warning |
| Device user shares VPP user accounts |
This alarm occurs when different users accept a VPP invitation using the same Apple ID and become Associated. |
Retire the alarmed user and have the re-created user accept the VPP invitation again with the correct Apple ID. |
Warning |
| Device has an inactive iTunes Store account |
A valid Apple ID is not configured on the managed device. |
After signing in with the Apple ID that accepted the VPP invitation on the managed device, the alarm will be cleared once the managed device and MDM server are synchronized. |
Warning |
| Device iTunes account differs from User iTunes account |
(iOS 8+) This alarm occurs when the user signs in on the managed device with a different Apple ID than the one that accepted the VPP invitation. |
After signing in with the Apple ID that accepted the VPP invitation on the managed device, the alarm will be cleared once the managed device and MDM server are synchronized. |
Warning |
| Device SIM card has been replaced |
This alarm is raised when SIM card change was detected. |
This alarm is cleared when Operator authorized changed SIM card or authorized SIM card. |
Critical |
| Unauthorized Shared iPad Login |
|
|
Warning |
| Media is not installable on the device |
|
|
Warning |
| Failed to install password policy because the device has no password |
This alarm is raised when a password policy is synced with a Windows 8.1 device, but the policy could not be applied to the device. |
Set password on the device before applying password policy on BizMobile Go! |
Warning |
| Contents of the specified folder cannot be removed when softwipe is performed on a device |
This alarm is raised when Selective wipe is performed on a device and contents of the specified folder cannot be removed. E.g. Folder is not found |
Operator can delete this alarm by trash icon once confirmed the reason of folder deletion was failed. |
Warning |
| Admin Lock could not be applied to the device. The command was sent to the device, but the device returned an error |
|
|
Warning |
| Profile is incompatible with the OS |
If a Template/Profile containing a Android 5 restriction is assigned to lesser than Android 5 device, an alarm will be raised for each Template. |
This alarm is cleared by below conditions; When the Profile is unassociated with the device When the Device is unassociated with the Template When Device is deleted When the Device withdrawn |
Warning |
| The device contains an old version of the Android agent that is not supported |
This alarm is raised when an Android device migrated from BizMobile to BizMobile Go! and the device has an old agent version. |
This alarm is cleared when agent on device is upgraded to a version supported by BizMobile Go!. |
Warning |
| Google profile is incompatible with the agent |
If a version of the agent installed to a device that is older than the version required to support Android 5 profile settings, an alarm will be raised for each Device. |
This alarm is cleared by below conditions; When the Profile is unassociated with the Device When the Device is unassociated with the Template When Device is deleted When the Device withdrawn When agent is compatible |
Warning |
| Google profile requires the device agent to be the device owner |
This alarm is raised if a Profile contains a policy setting that requires device owner mode, and the device agent is NOT a device owner. |
This alarm is cleared by below conditions; When the Profile is unassociated with the device When the Device is unassociated with the Template When Device is deleted When the device withdrawn |
Warning |
| Device owner installed an application that was prohibited by the blacklist/whitelist assigned to the device template |
Device owner installed an application that was prohibited by blacklist/whitelist which was assigned to device template. |
Need to ask device user to uninstall banned application from the device. |
Warning |
| Application does not have any more licenses to assign |
Insufficient number of distributable licenses in VPP application. |
Purchase additional licenses for VPP applications and collect the licenses from users who are not using the VPP applications to ensure that the licenses are available for distribution. |
Warning |
| Application is already installed |
(iOS only) This alarm is raised when “application auto management” is OFF and unmanaged applications already exist. |
This alarm is cleared by below conditions. When “application auto management” is ON When the unmanaged application has been deleted from the device When the device is unassociated with the template When the application is unassociated with the template When device is deleted When the device was withdrawn |
Warning |
| Application has been removed from iTunes |
This alarm is raised when AppStore application which was registered on BizMobile Go! has been removed from AppStore (iTunes). |
This alarm is cleared by below conditions. Application is removed from BizMobile Go! Application is registered in AppStore again |
Major |
| Application has been removed from Google Play Store |
|
|
|
| Converting an unmanaged app to managed failed |
(iOS only) This alarm is raised when "application auto management" is ON and unmanaged application already exist on the device while converting application to managed failed. |
For iOS8 or older, “application auto management” setting is always off. This alarm is cleared by below conditions. When the unmanaged application has been deleted from the device When the device is unassociated with the template When the application is unassociated with the template When device is deleted When the device was withdrawn |
Warning |
| Location service unavailable for MDM on the device |
This alarm is raised when location function is disabled on the device while MDM forces to get device location and share it with Device Management Operator. |
This alarm is cleared when device users enabled the device location function and share location information. |
Warning |
| Location services are set to "When in use" on the device |
When Location services is set to "when in use" for BizMessage and device Location Option is set to "Force location information sharing" |
The alarm can be removed by setting the location setting in the BizMessage app to "Always". |
Warning |
| Apple Push Certificate will expire in less than 7 days |
Apple Push Certificate (mandatory certificate for iOS device management) will be expired in 7 days. |
Please renew Apple Push Certificate following Renew Apple Push Certificate as soon as possible. |
Warning |
| Apple Push Certificate will expire in less than 30 days |
Apple Push Certificate (mandatory certificate for iOS device management) will be expired in 30 days. |
Please renew Apple Push Certificate following Renew Apple Push Certificate as soon as possible. |
Warning |
| Apple Push Certificate has been disabled |
This alarm is raised when iOS device enrollment was executed without registering MDM push certificate. |
Register MDM Push certificate before iOS device enrollment. Refer to the Obtain and register Apple Push Certificate for detail. |
Warning |
| Apple Push Certificate has expired |
Apple Push Certificate (mandatory certificate for iOS device management) was expired. |
Need to act immediately to register Apple Push Certificate and register all device again. |
Critical |
| Apple Push Certificate has been revoked |
Apple Push Certificate (mandatory certificate for iOS device management) was revoked. |
Need to act immediately to register Apple Push Certificate and register all device again. |
Critical |
| Apple VPP token has been registered with another management server. License management will not work correctly |
the VPP account has been marked as managed by another MDM service |
Use another Apple VPP account or disconnect from the MDM service that is being used. A VPP token and an MDM service must be associated one-to-one. If you wish to use VPP in multiple MDM environments, please separate the "locations" on Apple Business Manager. |
Warning |
| Apple VPP token will expire in 30 days |
This occurs when the Apple VPP token has one month left to expire. |
Update VPP token. |
Warning |
| Apple VPP token will expire in 7 days |
This occurs when the Apple VPP token has one week left to expire. |
Update VPP token. |
Warning |
| Apple VPP token has expired |
Unit VPP token has expired |
Update VPP token. |
Warning |
| A DEP-enrolled device has been re-enrolled |
This occurs when the DEP device is re-checked in. |
After confirmation, you can delete this alarm by clicking on the an icon on the far right. |
Warning |
| Apple DEP token will expire in 30 days |
This occurs when the Apple DEP token has one month left to expire. |
Update your Apple DEP token |
Warning |
| Apple DEP token will expire in 7 days |
This occurs when the Apple DEP token has one week left to expire. |
Update your Apple DEP token |
Warning |
| Apple DEP token has expired |
This occurs when the Apple DEP token expires. |
Update your Apple DEP token |
Warning |
| Zero-touch-enrolled device has been re-enrolled |
This occurs when the Zero Touch device is re-checked in. |
After confirmation, you can delete this alarm by clicking on the an icon on the far right. |
|
| External provisioning profile has expired |
Provisioning profile was expired. |
In-house application is not available. Please renew and register provisioning profile immediately. |
Minor |
| Embedded provisioning profile has expired |
Provisioning profile which is embedded in managed in-house application was expired. |
In-house application is already not available. Please renew and register provisioning profile or register rebuilt in-house application immediately. |
Minor |
| External provisioning profile will expire in 1 week |
Provisioning profile will be expired in 1 week. |
Please renew and register provisioning profile as soon as possible, otherwise in-house application will not be available. |
Minor |
| Embedded provisioning profile will expire in 1 week |
Provisioning profile which is embedded in managed in-house application will be expired in 1 week. |
Please renew and register provisioning profile or register rebuilt in-house application as soon as possible, otherwise the in-house application will not be available. |
Minor |
| External provisioning profile will expire in 1 month |
Provisioning profile will be expired in 1 month. |
Please renew and register provisioning profile as soon as possible, otherwise in-house application will not be available. |
Minor |
| Embedded provisioning profile will expire in 1 month |
Provisioning profile which is embedded in managed in-house application will be expired in 1 month. |
Please renew and register provisioning profile or register rebuilt in-house application as soon as possible, otherwise the in-house application will not be available. |
Minor |
| Microsoft Azure Client Secret Key has expired |
|
|
|